Model Files vs Deployed Models

In Pyramid data flows and models are designed using the Model app. In designing these items, users create their required logic, flows and settings and store them in a definition file, which is saved in the content management system. Access to the definition file is defined and managed like all other content files on the system through tools like the content manager.It can be copied, moved, deleted, shared and secured through the same mechanics that are applied to all other content items in Pyramid.

Definition Files

Model definition files, like all content files in the content manager, can be secured with roles (using the roles panel). However, the definition files can CONTAIN role security settings to be set or applied to the materialized data content created when the model file is run. The access rights determine which users can see (aka "read") the databases or data models and which ones can change them (aka "write"). These permissions are then saved in the model definition file and are materialized into the live database and / or live data model.

Once the materialized data artifacts have been created, admins can continue to administer and adjust these security settings through the Data Source Manager while model owners can administer the same security settings through the Materialized Data Manager - albeit with less scope and functionality.

Deployed Models

When a Model definition file is run and deployed, it "MATERIALIZES" a new database, data model or machine learning model. These materialized artifacts are separate entities and exist without the definition file. Further, they need to be secured and managed themselves using a different set of tools. The Materialized Data Manager for end-users is the tool for managing these materialized items while the Data Source Manager is the tool for admins.

Security

Model definition files can be secured with roles (using the roles panel). However, the definition files can CONTAIN role security settings to be set or applied to the materialized data content created when the model file is run. The access rights determine which users can see the databases or data models and which ones can change them. These permissions are then saved in the model definition file and are materialized into the live database and / or live data model.

Once the materialized data artifacts have been created, admins can continue to administer and adjust these security settings through the Data Source Manager while model owners can administer the same security settings through the Materialized Data Manager.